Processing actionable notifications

ABSTRACT

An actionable event notification disclosed herein provides actionable push notifications that allow an application server to collect information from end users. The actionable event notification includes a notification server that receives notification requests from application servers and communicates notifications to users where the notifications include specification for a notification UI form. In one implementation, the notification server modifies the callback identification on the notification from identification for the application server to identification for the notification server. A client device presents the notification UI form to a user to receive user responses. The user responses are communicated back to the notification server. The notification server processes the user responses and communicates them to the application server as necessary. Alternatively, the user responses are communicated directly to the application server requesting the notifications.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a Continuation of and claims benefit from orpriority of U.S. patent application Ser. No. 14/165,278, filed Jan. 27,2014, entitled “PROCESSING ACTIONABLE NOTIFICATIONS” which isspecifically incorporated by reference for all that it discloses andteaches.

The present application is related by subject matter to U.S. patentapplication Ser. No. 14/165,163 filed Jan. 27, 2014 and entitled“ACTIONABLE NOTIFICATIONS” which is specifically incorporated byreference herein for all that it discloses and teaches.

BACKGROUND

Modern communication technology and the growth of the Internet andwireless networks allow provision of various services to end usersthrough a wide variety of devices, such as computers, personal dataassistants, cell phones, smart phones, tablets, etc. Examples ofservices available through such devices include social networkapplications, gaming applications, traveling services, email, calendarservices, etc. For example, a user can connect to a social network,review news, receive travel updates, and receive emails, etc., usingsuch applications. The applications can also allow the users to receiveupdates about one or more news events, calendar updates, and newpostings on a social media network, etc. Such applications provide arich user experience via computing systems, such as mobile devices.Generally, application servers are used to provide backend servicesassociated with the application to the client computing systems. Forexample, an application server that hosts a social network applicationmay serve social network information to a social network clientapplication running on a mobile device.

Mobile devices face limitations relating to battery usage, networkcosts, etc. Therefore, many mobile platforms attempt to reduce batteryuse by minimizing the number of applications using the CPU and otherresources of the mobile device. Furthermore, to reduce the consumptionof battery and to reduce the network costs, mobile platforms may alsominimize the amount of time for which a mobile device communicates withand remains connected to services on the network.

SUMMARY

An actionable event notification disclosed herein provides actionablenotifications that allow an application service to collect informationfrom end users. The actionable event notification includes anotification server providing a notification service that receivesnotification requests from application servers providing applicationservices and communicates notifications to users where the notificationsinclude a specification defining a notification UI form to be presentedvia a user interface of a target device. The target device presents thenotification UI form to a user to receive user responses. The userresponses are communicated back to the notification service. Thenotification service processes the user responses and communicates themto the application service as necessary and/or processes them at thenotification service (e.g., redirecting them to another applicationserver or other destination). Alternatively, the user responses arecommunicated directly from the client devices to the application servicerequesting the notification. In one implementation, the notificationservice modifies the callback identification provided in thenotification request received from the application service, replacing itwith identification for the notification service.

In some implementations, articles of manufacture are provided ascomputer program products. One implementation of a computer programproduct provides a tangible processor-readable storage medium encoding aprocessor-executable program. Other implementations are also describedand recited herein.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates example data sources and flows for an actionableevent notification disclosed herein.

FIG. 2 illustrates example an example architecture for a notificationserver for the actionable event notification disclosed herein.

FIG. 3 illustrates example an example architecture for an applicationserver for the actionable event notification disclosed herein.

FIG. 4 illustrates example an example architecture for a client devicefor the actionable event notification disclosed herein.

FIG. 5 illustrates an example actionable notification provided on aclient device.

FIG. 6 illustrates example operations of a notification server disclosedherein.

FIG. 7 illustrates example operations of an application server disclosedherein.

FIG. 8 illustrates example operations of a client device disclosedherein.

FIG. 9 illustrates an example system that may be useful in implementingthe described technology.

FIG. 10 illustrates another example system that may be useful inimplementing the described technology.

DETAILED DESCRIPTION

To deliver information to applications running on client devices,application servers can use notification servers that send pushnotifications to the client devices. For example, in a scenario of anapplication server for a news application that sends breaking newsalerts to a mobile device, the news application server posts an eventnotification request to a notification server. The notification servermay already have a communication connection open to the mobile device,or it may open a communication connection in response to the eventnotification request received from the application server. Thenotification server delivers a notification to the mobile device usingthe communication connection. The operating system of the mobile deviceprocesses the notification and presents a visual, audio, or audio-visualnotice to the device user via a user interface of the mobile device.Alternatively, the mobile device may simply deliver the notification tothe mobile application for further processing. It should be understoodthat the client device (e.g., the target device) may be a mobile ornon-mobile device (e.g., a set top box, a gaming console, a desktopcomputer, etc.).

In various implementations, an actionable event notification disclosedherein facilitates efficient bi-directional communication between clientdevices and backend application servers providing services for variousapplications running on the client devices. For example, the actionableevent notification may facilitate efficient bi-directional communicationbetween an application server that hosts a social network applicationand a client device, such as a smartphone, that runs a social networkingapplication. In one implementation, an application server may use theactionable event notification disclosed herein to get feedback from aclient device without executing the client application on the clientdevice. For example, the actionable event notification may send anotification user interface (UI) form specification to the mobile deviceand an operating system of the mobile device may present a notificationUI form defined by the specification to the user without invoking orcommunicating with any mobile application.

Certain notifications, also referred to as “toasts,” where thenotification results in a graphical display that pops up over part of agraphical user interface display at the client device are useful toalert end users in a simple, immediate manner that does not overlydisrupt ongoing use of the client device by the end user. In variousexamples described herein, such notification systems at notificationservers and client devices are extended and enhanced to enableinformation from the client device to be communicated to thenotification server and/or application server. An actionablenotification system enables computing and communications workloads to bemoved away from the client device onto other entities such as thenotification server and/or application server. In some examples, anoperating system at the client device (such as a mobile phone, desktopcomputer, or gaming console) is modified and/or a notification UI formsprocessing module is provided at the client device. The actionablenotification system results in a better client device that uses itsresources more efficiently and/or is easier to write applicationsoftware for, from the point of view of the application serviceprovider. Usability is also improved for the end user of the clientdevice. For example, by using the UI form specification it is possibleto ensure the “look and feel” and/or style of the actionablenotifications are appropriate for the particular application service theactionable notifications are associated with. Actionable notificationsystems also make the actionable notifications more usable for the enduser. In addition, by using the actionable notifications the end userhas fast, immediate control of application services. When communicatingbetween a software application at the client device and an applicationserver, a web connection, such as a web socket, may be used. Such acommunication channel can time to establish, whereas using an actionablenotification service, the notification channel is already establishedand available between the notification service and the client device.

An implementation of the actionable event notification provides anotification UI form specification to the mobile device user to collectinformation from the user. For example, in response to a notificationrequest from a news application server, the actionable eventnotification presents a notification UI form via the user interface ofthe mobile device to collect input from the user, wherein thenotification UI form prompts the user to indicate whether the user isinterested in finding out more about a news story. That is, anotification UI form can be any combination of textual, visual, oraudible and/or graphical elements prompting a user to enter informationin an expected manner, such as by tapping an area of a touch screen,providing textual or voice input, capturing a video or still image, etc.An event notification server providing the event notification servicemay include or have access to a database of notification UI formspecifications for various application servers and various clientdevices. In such an implementation, when the actionable eventnotification receives a notification request from the applicationserver, the event notification server selects a notification UI formspecification from the database of notification UI form specifications,communicates the notification UI form specification to the mobiledevice, and requests the mobile device operating system to present thenotification UI form to the user without invoking a mobile application.In an alternative implementation, the actionable event notification mayrequest the mobile device operating system to analyze the informationprovided by the user via the notification UI form specification anddetermine whether to invoke a mobile application in response to theanalysis of the user provided information.

FIG. 1 illustrates example data sources and flows for an actionableevent notification 100 disclosed herein. The actionable eventnotification 100 facilitates communication across a network 120 betweenand/or among various users 102 and 104 and various application servers,such as an application server 106, using a notification server 108. Inone example, the application server 106 represents a voice over IP(VOIP) server that provides VOIP and instant messaging (IM) services(example “application services”) to users using various types ofdevices, such as mobile phones, smartphones, laptop computers, desktopcomputers, etc. An external event source 110, such as a news or RSS feed(alternative “application services”), may also communicate with thenotification server 108 using the network 120, such as the Internet, toprovide notifications to equipment of end users 102 and 104.

The users 102 and 104 may connect with the application server 106, thenotification server 108, and each other using the network 120. Forexample, the user 102 has a VOIP application installed on his or hersmartphone 122 that can be used to communicate with the user 104. Toinitiate communication with user 104, the user 102 sends a notificationrequest 130 to the application server 106. The application server 106processes the request to determine a target device to which it needs tosend a notification. The application server 106 may have a memory thatstores the mapping of various devices to users. Thus, the applicationserver 106 may use the mapping to identify a target mobile device 124.In the present case, if the user 102 has requested a connection with theuser 104, the application server 106 determines that it needs to send anotification to the target mobile device 124 (e.g., to notify the mobiledevice 124 of the incoming message).

To conserve battery power, the operating system of the mobile device 124generally attempts to reduce the number of client applications executingon the mobile device 124 at any time. For example, in oneimplementation, all of the applications that are not currently in use bythe user 104 may be terminated or suspended in order to conserve batterypower. Thus, the VOIP or IM applications on the mobile device 124 maynot be running when the request is sent from the user 102. Furthermore,to conserve the communication bandwidth used by the mobile device 124,the mobile device 124 may not have any open communication connectionswith the application server 106. Therefore, to send a notification tothe device 124, the application server 106 sends a notification request132 to the notification server 108. Another example of a notificationrequest to the notification server 108 includes an event notification134 from the event source 110, such as a news feed, that needs to send anews update to the user 104.

The notification request 132 may include, for example, event-identifyingcontent (e.g., a brief subset of the message, news item, etc.), acallback specification, a user identification, a device identification,etc. Both a user identification and a device identification can beconsidered a notification target identification, representing the targetdestination(s) that the application server is attempting to notify ofthe event. For example, for the application server 106 that provides asocial networking service, the notification request 132 may include anidentification of a client device used to view the social networkingupdates, an update on the social networking page (such as a newly postedcomment), and the specification of the expected callback from the user(such as a comment response), a like/dislike input, etc. Furthermore,the callback specification may also specify the social networking serveras the destination for any response from the user. In oneimplementation, the callback specification is provided in the form of auniform resource identifier (URI), a uniform resource locator (URL),etc.

The notification server 108 can modify the callback specification toidentify the notification server 108 instead of the application server106. In this manner, the notification server 108 can manage any responsefrom the mobile device 124. The notification server 108 can performappropriate operations in reaction to a received response, includingforwarding the response back to the application server 106 identified inthe original callback specification.

In one implementation, the notification request 132 from the applicationserver 106 also includes a notification UI form specification defining anotification UI form to be presented to the user 104. Alternatively, thenotification server 108 may determine an appropriate notification UIspecification to associate with the notification. In yet anotheralternative, the notification request 132 may include a request toinvoke (e.g., initiate execution, bring to the foreground) anappropriate application on the client device 124. For example, in thecase of the application server 106 being a VOIP application server, thenotification request 132 may specify invoking a VOIP application on thedevice 124.

Upon receiving a notification request 132, the notification server 108determines the source of the notification request 132, theevent-identifying content of the notification request 132, and a targetdevice. For example, the notification request 132 from a VOIPapplication server specifies a mobile device (e.g., a phone number) thatis the intended destination for a notification. Alternatively, thenotification request 132 may only specify a user or group of users as aless-specific destination for the notification (e.g., a user), in whichcase, the notification server 108 determines one or more target devicesassociated with the user or group of users.

The notification server 108 may include a redirection module thatdetermines the destination for the notification 136 and sends anotification 136 to such device. Furthermore, the notification server108 also includes a database of notification UI form specifications thatthe notification server 108 associates with the notification 136. Forexample, upon receiving a VOIP notification request 132, thenotification server 108 selects a notification UI form specificationthat defines a notification UI form that requests the user 104 tospecify whether the user 104 is interested in taking a VOIP call on themobile device 124 and associates the selected notification UI formspecification with the notification 136. The associated notification UIform specification can be sent with or otherwise is associated with thenotification 136 to the mobile device 124.

Alternatively, the notification UI form may request the user 104 tospecify an alternative device where the user 104 would like to receivethe VOIP call. For example, if the user 104 has the capability toreceive the VOIP call using the mobile device 124 and a computer 126,the notification UI form may present two selection buttons from whichthe user 104 can select a desired target device.

The mobile device 124 may present the notification UI form to the user104 using the operating system of the mobile device 124 and withoutinvoking the VOIP application on the mobile device 124. For example, thenotification UI form may collect input from the user, such as “ignorethis call” and then send the user's “ignore” response back to thenotification server 108 without invoking the VOIP application on themobile device 124. In some other examples, the mobile device 124presents the notification UI form using the operating system of thedevice 124 and may also invoke the VOIP application, whetherconcurrently or subsequently to processing of the notification UI formby the operating system. For example, the installed VOIP application maybe fully invoked in the foreground or invoked in the background to allowthe operating system and/or notification UI form to extract informationfrom the installed application. In yet another alternativeimplementation, the VOIP application is invoked only after receiving oneor more inputs from the user 104 through the notification UI form in theuser interface of the mobile device 124. Furthermore, the mobile device124 may also revise the notification UI form presented to the user 104based on various parameters about the user 104, such as the user'spreferences, location, etc.

The mobile device 124 collects the information provided by the user 104through the notification UI form presented in the user interface of themobile device 124 and sends a UI response 140 to the notification server108. These collecting and sending operations may be performed by theoperating system of the mobile device 124 (or another target device).Thus, for example, in the case of a VOIP notification, the mobile device124 collects the information provided by the user 104 via thenotification UI form as to whether the user 104 wants to accept the VOIPcall, etc., and sends the information as a UI response 140 to thenotification server 108. The notification server 108 processes the UIresponse 140 and generates a notification response 142 to theapplication server 106. For example, if the user 104 has indicated adesire to receive the VOIP call at a specific later time, thenotification server 108 generates the notification response 142including the specified time to the application server 106.

Alternatively, after processing the notification UI form, the mobiledevice 124 may determine to activate an application on the mobile device124. Thus, in response to the notification UI form related to the VOIPrequest, the mobile device 124 may activate the VOIP application.Subsequently, the VOIP application on the client device directly sendsan application response 144 to the application server 106. For example,the application response 144 may include acceptance of the VOIP callfrom the user 104. The application server 106 processes the notificationresponse 142 and/or the application response 144 and generates a userresponse 146 to the user 102.

Thus, the actionable event notification 100 facilitates communicationbetween various users, application servers, event sources, etc., withefficient utilization of the existing and ongoing communicationconnection between the mobile device 124 and the notification server 108(that is available as a result of the push notification service beingprovided to the mobile device by the notification server). No newcommunication channel between the application server 106 and the mobiledevice 124 need be established. Furthermore, as the mobile device 124does not have to invoke the applications on the device to collectinformation from the user 104, the actionable event notification 100conserves the battery power on the client device 124. Usability is alsoimproved for the end user of the mobile device 124.

It should be understood that each application service and eachnotification service may be managed by multiple, distributed applicationservers and notification servers with a variety of optimizationsincluding load balancing, optimized routing, and resource management. Anapplication server or a notification server may take the form of asingle server system or multiple distributed server systems.

FIG. 2 illustrates an example architecture for a notification server 200for the actionable event notification disclosed herein. The notificationserver 200 includes a network interface module 202 that is configured tocommunicatively connect to various application servers 206 and a deviceinterface module 204 that is configured to communicate with variousclient devices 208. It should be understood that the interface modules202 and 204 may be integrated and may interface with a single network orwith different networks. The notification server 200 may be implementedon an application server or on a dedicated server with high-speedcommunication connections to networks, such as the Internet. In oneimplementation, the notification server 200 has at least one existingand ongoing communication connection with each of the client devices208. The notification server 200 is configured to send pushnotifications to the devices 208 via existing and ongoing communicationconnections (such as TCP channels). The application servers 206 maycommunicate with the notification server 200 using a high-speed,high-capacity binary asynchronous interface, etc. For example, in oneimplementation, the application servers 206 communicate with thenotification server 200 using an HTTP POST request over a secure socketslayer (SSL). In some implementations, such communication channels may bebi-directional. For example, the notification server 200 may post to anapplication server 206 certain user feedback collected via anotification UI form on a client device 208.

It should be understood that the notification UI form may also providean amount of rich user interface activity. For example, an applicationserver can specify that the notification UI form provides an alert thatinterrupts the user through the user interface and allows the user topin the alert to a particular user interface tile, add some informationfrom the alert's payload to the user's calendar, etc. Other actions maybe made available through the notification UI form presented through theuser interface of the client device.

An implementation of the notification server 200 also includes anauthentication module 212 to authenticate notification requests receivedfrom the applications servers 206 and a validation module 214 tovalidate such notification requests. For example, the authenticationmodule 212 authenticates the source of the notification request toensure that only legitimate notification requests are processed by thenotification server 200. In another implementation, the validationmodule 214 validates the payload or content included in the notificationrequest. Example content included in a notification request may be amessage to a target user, an identification of the target user, anotification UI form specification to be sent to the target device, etc.Accordingly, the validation module 214 can validate the content of thenotification request to ensure that the request does not include anymalicious code, virus, etc.

The notification server 200 also includes a prefetch module 216 thatprefetches information used to service the notification request. Forexample, after analyzing the notification request, the prefetch module216 fetches a notification UI form specification from a notification UIform database 230. Notification UI form specifications define anotification UI form that can be presented via a user interface at atarget device. The prefetch module 216 may use the source, destination,and/or content of the notification request, among other parameters, todetermine the notification UI form specification to be used to servicethe notification request. In one implementation, an application server206 may have provided a specific notification UI form specification tobe used to service a specific type of notification request. Thus, thenotification UI forms database 230 can store such notification UI formspecifications by the source of notification requests, the destinationfor the notification UI form specifications, the type and/or content ofnotification requests, etc. For example, if the notification request isfrom a VOIP application server for a VOIP message request, a VOIP-basednotification UI form specification is used. On the other hand, adifferent notification UI form specification is used for a notificationrequest from an IM server for an IM message. In yet anotherimplementation, a first VOIP server may employ a notification UI formthat collects information regarding a recipient's willingness to take aVOIP call, whereas another VOIP server may employ a notification UI formthat also collects information about the recipient's preferred device onwhich to take the call.

In another implementation of the prefetch module 216, UI components of anotification UI form, such as images, audio, icons, etc. may becollected and prepared (e.g., formatted for a particular display of atarget device). The UI components may be combined with the notificationUI form selected by the prefetch module 216 at the notification server216. Alternatively, certain UI components may be sent to the targetdevice separately from the notification UI form, wherein the targetdevice (e.g., the operating system on the target device) combines the UIcomponents with the received notification UI form before presentation ofthe notification form to the user on the target device.

The notification server 200 may also include a user channel database 232that stores information regarding communication connections related tovarious users. In one implementation, the channel information iscategorized by the client devices (e.g., as identified by a deviceidentification). Alternatively, the channel information is categorizedby user identification or another channel-influencing factor. Forexample, the user channel database 232 includes information aboutchannels related to each VOIP identification associated with a specificdevice, each VOIP identification associated with a specific user, etc.

A form modification module 218 can modify the notification UI formspecification as necessary based on the content from the notificationrequest, the identification of the request source and/or target device,or other parameters. Example modification may include without limitationchanging the notification UI form to support a particular type of targetdevice (e.g., mobile phone versus game console versus portablecomputer), simplifying the format of a received notification UI formfrom a rich format to a less-rich format compatible with a target devicewith less sophisticated display capabilities (e.g., simplifying an richgraphical notification UI form to a text-only UI form for a low endmobile phone with limited display capabilities). The form modificationmodule 218 associates the modified UI form specification with anoutgoing notification to one of the client devices 208. A redirectionmodule 220 redirects the notification together with the appropriatenotification UI form specification to one of the client devices 208.

FIG. 3 illustrates an example architecture for an application server 300for the actionable event notification disclosed herein. The applicationserver 300 includes a notification server interface 302 to communicatewith a notification server 306 and a user interface 304 to communicatewith various client devices 308. A push notification module 310generates push notification requests to be sent from the applicationserver 300 to the notification server 306. For example, if a clientdevice 308 requests an IM connection to another device via theapplication server 300 providing IM service, the push notificationmodule 310 generates a notification request for sending a notificationto the other device. In such a case, the notification server interface302 communicates the notification request to the notification server 306to send an IM request to the target device. The push notification module310 may also generate callback URLs that are included with thenotification requests sent by the application server 300 to thenotification server 306. Such callback URLs may specify that clientdevice responses to the notification may be sent back to the applicationserver 300 or to some other destination. In some implementations, thenotification server 306 may modify the callback URL so that the clientdevice sends responses back to the notification server 306, rather thanthe original callback URL specified by the application server 300.

The application server 300 also includes a user registration module 324that registers users' devices 308 on the application server 300. Theuser registration may include, for example, user account information,user identifications, passwords, etc. Thus, for the application server300 providing IM services, the user registration module 324 may includethe information about the identification of client devices related tothe user, such as the phone numbers for the mobile devices, computeridentification, email address, etc. An events-users mapping module 326stores mapping of events to various users. For the application server300 providing news services, the events-users mapping module 326 storesinformation about which news events shall be provided to a particularuser, etc. For example, a first user may be interested in gettingupdates related to sports events, whereas a second user may beinterested in getting updates related to political events, etc. In sucha case, the events-users mapping module 326 maps the source of sportsevents updates to the first user and the sources of political eventupdates to the second user. Similarly, for the application server 300providing VOIP services, the events-users mapping module 326 maps a VOIPrequest from a calling user to a target user.

Other examples of user responses collected by the notification UI formand processed by the notification server 306 or application server 300may include without limitation whether the user accepts or declines aVOIP call, whether the user “likes” the received content, a responsemessage to be posted back to the social media network, etc.

A form construction and modification module 328 constructs and/ormodifies notification UI form specifications defining a notification UIform used to communicate an event to a user via the user interface ofone of the client devices 308. For example, for an event related to aVOIP request, the form construction and modification module 328constructs or modifies a notification UI form specification defining anotification UI form that requests a target user to specify his or herwillingness to take a VOIP call. The form construction and modificationmodule 328 may use notification UI form specifications stored in anotification UI forms database 332 and modify such UI formspecifications as appropriate. The application server 300 also includesa client device information database 334 that includes information aboutthe client devices 308, such as the make and model of a client device,etc. The form construction and modification module 328 may also use theinformation from the client device information database 334 to modify anotification UI form specification selected from the notification UIforms database 332. For example, if a notification UI form specificationis constructed for presentation on a device with a Flash playercapability and a client device does not have a Flash player capability,the form construction and modification module 328 can modify suchnotification UI form specification accordingly.

The application server 300 also includes a callback receiving module 312that is configured to receive callbacks received from the notificationserver 306 or client devices 308. The callback receiving module 312communicates the received callbacks to a callback processing module 330that processes the callbacks from the notification server 306.Processing the callbacks may involve, for example, processing theinformation provided by a user in response to a notification UI formpresented to the user, constructing a response message, opening anothercommunication, etc. For example, for an application server 300 providingVOIP services, if the callback from the notification server 306specifies that a user wants to receive a VOIP call at an alternativedevice, the callback processing module 330 can generate a VOIP requestto be sent to the alternative device.

FIG. 4 illustrates an example architecture for a client device 400 forthe actionable event notification disclosed herein. The client device400 may be, for example, a mobile phone, a laptop, a gaming console, aset-top box, a smartphone, etc. The client device 400 includes anotification server interface 402 that communicates with a notificationserver 406 and an application server interface that communicates withvarious application servers 408. The notification server interface 402may receive push notifications from the notification server 406 whereinthe push notifications may include a notification UI form specificationdefining a notification UI form to be presented to a user. Anotification processing module 410 processes the information received inthe notification. For example, the notification processing module 410may analyze a notification to determine the destination module on theclient device 400 to receive content from the notification. Thus, if thenotification requests invoking an application on the client device 400,the notification processing module 410 invokes an application from anapplication database 432. The application database 432 may includeexecutable files for various applications that are configured to executeon the client device 400.

In various examples, the operating system 430 of the client device isenhanced to enable actionable notifications. If the notificationinstructs the client device 400 to present a notification UI form to auser without invoking any application, the operating system 430processes the notification by presenting the notification UI formdefined by the notification UI form specification received inassociation with the notification. For a notification including orassociated with a notification UI form specification, the operatingsystem 430 uses a notification UI forms processing module 428 to processthe notification UI form specification and to present the notificationUI form to the user. An input/output module 426 presents thenotification UI form on the client device 400 using device outputresources, such as a touch screen, and received input from the userusing an input such as a keyboard. A content receiving module 424receives content from a user information database 434 for use by theinput/output module 426. Thus, the notification UI form presented to theuser may be populated by various default or other user informationstored on the user information database 434.

The notification UI forms processing module 428 collects the informationprovided by a user in response to the notification UI form anddetermines whether to invoke an application from the applicationdatabase 432 or to return a postback notification to the notificationserver 406. Example user input is not limited to keyboard input but mayalso include without limitation voice responses, still or video imagedata captured by a mobile camera or other input devices, etc. A postbackmodule 412 generates the postback notification that is communicatedthrough the notification server interface 402 to the notification server406. In some implementations, the postback module 412 may prepare theresponse to the appropriate server, such as by packing local data,compressing the local data, and/or signing it before returning it to theserver.

In various implementations, any one or more of: the content receivingmodule 424, the input/output module 426 and the notification UI formsprocessing module 428 may be integral, in whole or in part, with theoperating system 430.

In an example, a mobile communications device or other target devicecomprises an operating system arranged to receive a notification messagefrom a notification server with which the device is in substantiallycontinual communication; the operating system arranged to parse anotification UI form specification from the received notificationmessage, to use the UI form specification to display a UI form at adisplay of the mobile communications device, to receive user input inresponse to the displayed UI form, and to communicate with any of thenotification server and an application server on the basis of thereceived user input.

FIG. 5 illustrates an example actionable notification as presented in anotification UI form 500 provided on a client device 502 in response toa notification. The notification UI form 500 may be provided to the userin response to a notification request from an application server 504 toa notification server 506. The notification UI form 500 is processed andpresented by the operating system of the client device 502 and mayinclude a text notification 510 including the content of thenotification that is displayed on the client device 502. As an example,the illustrated notification UI form 500 also includes a picture/logo512 that may identify the application server that initiates thenotification.

In one implementation, the application server 504 may be a VOIP servicethat sends a notification to the user about a request for a VOIPsession. In this case, the text notification 510 notifies the user thatanother user has requested a VOIP session with the user of the device502. The text notification 510 may include information about the userrequesting the VOIP session and other information identifying the VOIPsession. The picture/logo 512 may identify the VOIP application server.The notification UI form 500 also includes a comment field 520 that canbe used by a user to input his or her comments. Other example UIcomponents may include video and/or audio clips, voice messages, stillimages, avatars, icon, etc.

An input field 530 of the notification UI form 500 provides a number ofinput choices 532, 534, and 536 that a user can select to submit achoice (e.g., a choice of another target device to which to redirect thenotification, a choice of another target device on which to execute anaction). For example, for the notification UI form 500 related to a VOIPservice notification, the input field 530 includes input choices relatedto the device that the user would like to use for a VOIP session. In oneimplementation, the selection of input fields 532-536 is based oninformation about the user that is known to the notification server 506.Thus, if the notification server 506 may know that based on past usage,the user has VOIP applications installed on each of a desktop, a tablet,and a smartphone. Therefore, the notification UI form 500 presents inputchoices for these three devices. In an alternative implementation, theinput field 530 may also be a drop down list, or an input field wherethe user can manually provide the requested information. Example userinput is not limited to keyboard input but may also include withoutlimitation voice responses, still or video image data captured by amobile camera or other input devices, etc.

In addition, other notification UI forms may collect other user input,such as whether to accept a VOIP call, whether a client “likes” receivedcontent, etc. The notification UI form type can vary with the targetdevice, with the destination user, with the type of application service,etc.

A submit button 540 allows the user to save and submit the informationprovided using the notification UI form 500. In one implementation, theinformation from the notification UI form 500 is not processed at thedevice 502 and is sent to the notification server 506 for furtherprocessing. Alternatively, an operating system of the device 502 mayprocess the information from the notification UI form 500 to make one ormore decisions at the device level. For example, the operating system ofthe device 502 may initiate a VOIP application on the device 502 inresponse to the inputs received from the user. The notification server506 processes the information collected from the notification UI form500 and communicates with the application server 504 as necessary.

FIG. 6 illustrates example operations 600 of a notification serverdisclosed herein. A receiving operation 602 receives a notificationrequest from an application server, such as a VOIP service, an IMservice, etc. For example, the receiving operation 602 receives thenotification request over a secure socket layer (SSL) from anapplication service. The notification request may include a message to atarget user or target device, an identification of the target user ortarget device, a notification UI form to be sent to the target user ortarget device, etc. An authenticating operation 604 authenticates thenotification request to ensure that the notification request is receivedfrom an authenticated application service. A validating operation 606validates the notification request to ensure that there is no maliciouscode in the notification request received from the application server.

An analysis operation 608 analyzes the notification request to determinevarious operations to be taken in response to the notification request.For example, the analysis operation may determine the identity of thetarget user, the device used by the target user, a communicationconnection that is used to communicate with the target user, thecapabilities of the device used by the target user, etc.

A determining operation 610 determines and/or modifies a notification UIform specification related to the notification request. For example, thedetermining operation 610 may select a notification UI formspecification from a notification UI form database at the notificationserver. Alternatively, the notification request from the applicationserver may include a notification UI form specification. The determiningoperation 610 may also modify the selected notification UI formspecification associated with the notification request based on variousparameters related to the user receiving the notification, the clientdevice used to display the notification, etc. Some examples may includethe visual form factor of the client device (e.g., available screen realestate), hardware performance capabilities of the client device,available communication bandwidth, network reliability, etc. Forexample, the determining operation 610 can change one or more controls,input boxes, etc., to be displayed in a notification UI form based onthe type of device used by the user receiving the notification. Thus, ifthe client device does not include a color display, the notification UIform can be modified to be displayed in greyscale. Alternatively, thedetermining operation 610 changes the specification for the notificationUI form based on the bandwidth of a channel used to communicate with theclient device, with a higher resolution notification UI form used for ahigher bandwidth channel and a lower resolution notification UI formused for a lower bandwidth channel.

A modifying operation 612 may modify one or more callback specificationsfrom the notification request. Thus, if an application server for VOIPservices has sent a notification to the notification server with acallback specification specifying the VOIP service as the callbackdestination, the modifying operation 612 can modify such callbackspecification to specify the notification server as the callbackdestination. For example, the modifying operation 612 may modifycallback specification so that the callback destination is a URL/URIidentifying the notification server.

A sending operation 614 sends a notification to a target device. Thetarget device is selected based on the information provided in thenotification request, information about users stored at the notificationserver, etc. In one implementation, the notification server has a memorythat stores information about communication connections for variousclient devices. The sending operation 614 selects one of suchconnections and sends the notification to the client device over theselected connections.

A receiving operation 616 receives user responses from client devices.For example, the receiving operation 616 receives a user response to anotification about a VOIP session request sent to a client device. Inone implementation, the user response includes information provided bythe user provided through a notification UI form presented to the useralong with the notification. In the example where the notificationincludes a VOIP session request, the user response may include theuser's willingness to participate in the VOIP session, an identificationof an alternative device used to participate in the VOIP session, analternate time suggested by the user for the VOIP session, etc.

A processing operation 618 processes the user response to determine anappropriate action. For example, based on the content of the userresponse, the processing operation 616 may form a notification responsethat should be sent to the application server that originated thenotification request. A sending operation 620 sends the notificationresponse to the application server.

FIG. 7 illustrates example operations 700 of an application serverdisclosed herein. An analysis operation 702 analyzes an event determinedby the application service or a related service. For example, if theapplication server that provides a social networking applicationservice, the analysis operation 702 may analyze a posting by a user on asocial networking website. A determining operation 704 determines if theapplication server needs to send a notification to a user in response tothe event. If it is determined that a notification is to be sent,another determination operation 706 determines if a notification UI formspecification is to be associated with the notification. If anotification UI form specification is indicated, a selecting operation708 selects a notification UI form specification from a notification UIform database on the application server and associates the notificationUI form specification with a notification to be sent to a target device.

A sending operation 710 sends the notification request to a notificationserver with or without the notification UI form specification. Thenotification request may also include other content such as anidentification of a user, the content to be displayed to the user, theclient device identification, etc. A receiving operation 712 receives anotification response from the notification server. The notificationresponse may include information provided by a user via a notificationUI form displayed on a client device. A determining operation 714processes the notification response to determine whether a communicationconnection needs to be opened to communicate directly with a clientdevice. If so, a communications operation 716 opens a communicationconnection for directly communicating with a client device.

FIG. 8 illustrates example operations 800 of a client device disclosedherein. In one implementation, the operations 800 are executed by anoperating system of the client device without invoking a relatedapplication on the client device. Alternatively, the operating system ofthe client device may invoke an application on the client device whereinthe application executes some of the operations 800.

A receiving operation 802 (e.g., of a client device operating system orof an application at the client device) receives a notification from anotification server. The notification may include, for example, contentto be displayed to a user, a notification UI form that is presented tothe user, etc. The notification is associated with an application thatis installed on the client device. The notification may also beassociated with a particular device, a particular user, or a particularhardware or software component on the client device. An authenticatingand validating operation 804 authenticates and/or validates thenotification to ascertain the source of the notification, the content ofthe notification, etc. A processing operation 806 (e.g., of a clientdevice operating system or of an application at the client device)processes the notification. Such processing may include determining anapplication on the client device that the notification pertains to,determining any notification UI form specification associated with thenotification, determining any default content that can be used to updatethe notification UI form specification, etc. For example, if thenotification is related to a social networking application and includesa notification UI form specification including input fields for “like,”“dislike,” etc., the processing operation 806 may select appropriateicons for presenting such input fields.

A presenting operation 808 (e.g., of a client device operating system orof an application at the client device) presents the notification UIform on the client device. An example of the notification UI formincludes a message to the user, a logo identifying an application, aninput field for free form content from the user, an input fieldproviding various options to the user, an input field in the form of adrop-down list, a submit option, etc. A receiving operation 810 (e.g.,of a client device operating system or of an application at the clientdevice) receives user inputs via the notification UI form. A determiningoperation 812 processes the user inputs to determine if an applicationis to be invoked on the client device. If so, an operation 814 (e.g., ofa client device operating system or of an application at the clientdevice) invokes an application and sends content to the application,wherein the content sent to the application includes content receivedwith the notification, the content received through the notification UIform, etc. A sending operation 816 (e.g., of a client device operatingsystem or of an application at the client device) forms a response andsends the response to the notification server.

FIG. 9 illustrates an example system that may be useful in implementingthe described technology. The example hardware and operating environmentof FIG. 9 for implementing the described technology includes a computingdevice, such as general purpose computing device in the form of a gamingconsole or computer 20, a mobile telephone, a personal data assistant(PDA), a set top box, or other type of computing device. In theimplementation of FIG. 9, for example, the computer 20 includes aprocessing unit 21, a system memory 22, and a system bus 23 thatoperatively couples various system components including the systemmemory to the processing unit 21. There may be only one or there may bemore than one processing unit 21, such that the processor of computer 20comprises a single central-processing unit (CPU), or a plurality ofprocessing units, commonly referred to as a parallel processingenvironment. The computer 20 may be a conventional computer, adistributed computer, or any other type of computer; the invention isnot so limited.

The system bus 23 may be any of several types of bus structuresincluding a memory bus or memory controller, a peripheral bus, aswitched fabric, point-to-point connections, and a local bus using anyof a variety of bus architectures. The system memory may also bereferred to as simply the memory, and includes read only memory (ROM) 24and random access memory (RAM) 25. A basic input/output system (BIOS)26, containing the basic routines that help to transfer informationbetween elements within the computer 20, such as during start-up, isstored in ROM 24. The computer 20 further includes a hard disk drive 27for reading from and writing to a hard disk, not shown, a magnetic diskdrive 28 for reading from or writing to a removable magnetic disk 29,and an optical disk drive 30 for reading from or writing to a removableoptical disk 31 such as a CD ROM, DVD, or other optical media.

The hard disk drive 27, the magnetic disk drive 28, and the optical diskdrive 30 are connected to the system bus 23 by a hard disk driveinterface 32, a magnetic disk drive interface 33, and an optical diskdrive interface 34, respectively. The drives and their associatedcomputer-readable media provide nonvolatile storage of computer-readableinstructions, data structures, program modules and other data for thecomputer 20. It should be appreciated by those skilled in the art thatany type of computer-readable media which can store data that isaccessible by a computer, such as magnetic cassettes, flash memorycards, digital video disks, random access memories (RAMs), read onlymemories (ROMs), and the like, may be used in the example operatingenvironment.

A number of program modules may be stored on the hard disk, magneticdisk 29, optical disk 31, ROM 24, or RAM 25, including an operatingsystem 35, one or more application programs 36, other program modules37, and program data 38. A user may enter commands and information intothe personal computer 20 through input devices such as a keyboard 40 andpointing device 42. Other input devices (not shown) may include amicrophone, joystick, gamepad, satellite dish, scanner, or the like.These and other input devices are often connected to the processing unit21 through a serial port interface 46 that is coupled to the system busbut may be connected by other interfaces, such as a parallel port, gameport, or a universal serial bus (USB). A monitor 47 or other type ofdisplay device is also connected to the system bus 23 via an interface,such as a video adapter 48. In addition to the monitor, computerstypically include other peripheral output devices (not shown), such asspeakers and printers.

The computer 20 may operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer 49.These logical connections are achieved by a communication device coupledto or a part of the computer 20; the invention is not limited to aparticular type of communications device. The remote computer 49 may beanother computer, a server, a router, a network PC, a client, a peerdevice or other common network node, and typically includes many or allof the elements described above relative to the computer 20, althoughonly a memory storage device 50 has been illustrated in FIG. 9. Thelogical connections depicted in FIG. 9 include a local-area network(LAN) 51 and a wide-area network (WAN) 52. Such networking environmentsare commonplace in office networks, enterprise-wide computer networks,intranets, and the Internet, which are all types of networks.

When used in a LAN-networking environment, the computer 20 is connectedto the local network 51 through a network interface or adapter 53, whichis one type of communications device. When used in a WAN-networkingenvironment, the computer 20 typically includes a modem 54, a networkadapter, a type of communications device, or any other type ofcommunications device for establishing communications over the wide areanetwork 52. The modem 54, which may be internal or external, isconnected to the system bus 23 via the serial port interface 46. In anetworked environment, program engines depicted relative to the personalcomputer 20, or portions thereof may be stored in the remote memorystorage device. It is appreciated that the network connections shown areexample and other means of and communications devices for establishing acommunications link between the computers may be used.

In an example implementation, a notification server, various applicationservers, and other engines and services may be embodied by instructionsstored in memory 22 and/or storage devices 29 or 31 and processed by theprocessing unit 21. A user profile, user requests, information about auser's social network, and other data may be stored in memory 22 and/orstorage devices 29 or 31 as persistent datastores. Further, anotification server represents hardware and/or software configured toprovide service functionality for network-connected systems. Suchservices may be implemented using a general purpose computer andspecialized software (such as a server executing service software), aspecial purpose computing system and specialized software (such as amobile device or network appliance executing service software), or othercomputing configurations.

The terms “module,” “program,” “service,” and “engine” may be used todescribe an aspect of the computer 20 that is implemented to perform oneor more particular functions. In some cases, such a module, program,service, or engine may be instantiated via processing unit 21 executinginstructions held by system memory 22. It is to be understood thatdifferent modules, programs, and/or engines may be instantiated from thesame application, service, code block, object, library, routine, API,function, etc. Likewise, the same module, program, and/or engine may beinstantiated by different applications, services, code blocks, objects,routines, APIs, functions, etc. The terms “module,” “program,” and“engine” are meant to encompass individual or groups of executablefiles, data files, libraries, drivers, scripts, database records, etc.

FIG. 10 illustrates another example system (labeled as a mobile device1000) that may be useful in implementing the described technology. Themobile device 1000 includes a processor 1002, a memory 1004, a display1006 (e.g., a touchscreen display), and other interfaces 1008 (e.g., akeyboard). The memory 1004 generally includes both volatile memory(e.g., RAM) and non-volatile memory (e.g., flash memory). An operatingsystem 1010, such as the Microsoft Windows® Phone operating system,resides in the memory 1004 and is executed by the processor 1002,although it should be understood that other operating systems may beemployed.

One or more applications 1012 are loaded in the memory 1004 and executedon the operating system 1010 by the processor 1002. Examples ofapplications 1012 include without limitation email programs, schedulingprograms, personal information managers, Internet browsing programs,multimedia player applications, etc. A notification manager 1014 is alsoloaded in the memory 1004 and is executed by the processor 1002 topresent notifications to the user. For example, when a promotion istriggered and presented to the shopper, the notification manager 1014can cause the mobile device 1000 to beep or vibrate (via the vibrationdevice 1018) and display the promotion on the display 1006.

The mobile device 1000 includes a power supply 1016, which is powered byone or more batteries or other power sources and which provides power toother components of the mobile device 1000. The power supply 1016 mayalso be connected to an external power source that overrides orrecharges the built-in batteries or other power sources.

The mobile device 1000 includes one or more communication transceivers1030 to provide network connectivity (e.g., mobile phone network,Wi-Fi®, BlueTooth®, etc.). The mobile device 1000 also includes variousother components, such as a positioning system 1020 (e.g., a globalpositioning satellite transceiver), one or more accelerometers 1022, oneor more cameras 1024, an audio interface 1026 (e.g., a microphone, anaudio amplifier and speaker and/or audio jack), and additional storagedevices 1028. Other configurations may also be employed.

In an example implementation, a mobile operating system, variousapplications, and other modules and services may be embodied byinstructions stored in memory 1004 and/or storage devices 1028 andprocessed by the processor 1002. User preferences, service options, andother data may be stored in memory 1004 and/or storage devices 1028 aspersistent datastores.

Mobile device 1000 and computer 20 may include a variety of tangiblecomputer-readable storage media and intangible computer-readablecommunication signals. Tangible computer-readable storage can beembodied by any available media that can be accessed by the mobiledevice 1000 or the computer 20 and includes both volatile andnonvolatile storage media, removable and non-removable storage media.Tangible computer-readable storage media excludes intangiblecommunications signals and includes volatile and nonvolatile, removableand non-removable storage media implemented in any method or technologyfor storage of information such as computer readable instructions, datastructures, program modules or other data. Tangible computer-readablestorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CDROM, digital versatile disks (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othertangible medium which can be used to store the desired information andwhich can accessed by mobile device 1000 or computer 20. In contrast totangible computer-readable storage media, intangible computer-readablecommunication signals may embody computer readable instructions, datastructures, program modules or other data resident in a modulated datasignal, such as a carrier wave or other signal transport mechanism. Theterm “modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal.

The embodiments of the invention described herein are implemented aslogical steps in one or more computer systems. The logical operations ofthe present invention are implemented (1) as a sequence ofprocessor-implemented steps executing in one or more computer systemsand (2) as interconnected machine or circuit engines within one or morecomputer systems. The implementation is a matter of choice, dependent onthe performance requirements of the computer system implementing theinvention. Accordingly, the logical operations making up the embodimentsof the invention described herein are referred to variously asoperations, steps, objects, or engines. Furthermore, it should beunderstood that logical operations may be performed in any order, unlessexplicitly claimed otherwise or a specific order is inherentlynecessitated by the claim language.

The above specification, examples, and data provide a completedescription of the structure and use of exemplary embodiments of theinvention. Since many embodiments of the invention can be made withoutdeparting from the spirit and scope of the invention, the inventionresides in the claims hereinafter appended. Furthermore, structuralfeatures of the different embodiments may be combined in anotherembodiment without departing from the recited claims.

What is claimed:
 1. A processor-implemented method comprising:receiving, at a client device, a notification including a notificationUI form specification, and a callback specification, the notificationbeing sent to the client device in response to a notification requestreceived from an application server associated with an applicationinstalled on the client device, and the callback specificationspecifying both an expected callback from a user in response to thenotification and a uniform resource identifier (URI) or uniform resourcelocator (URL), the notification pertaining to the application installedon the client device; displaying, by the client device and withoutinvoking the installed application, a notification UI form for thereceived notification and defined by the notification UI formspecification in a user interface of the client device, the notificationUI form including at least one input control; collecting user inputassociated with the installed application via the at least one inputcontrol of the notification UI form displayed in the user interface ofthe client device according to the callback specification withoutinvoking the installed application; and communicating the collected userinput to the application server associated with the installedapplication that the notification pertains to according to the callbackspecification without invoking the installed application.
 2. Theprocessor-implemented method of claim 1 further comprising:authenticating the received notification before displaying thenotification UI form in the user interface of the client device.
 3. Theprocessor-implemented method of claim 1 further comprising: validatingthe received notification before displaying the notification UI form inthe user interface of the client device.
 4. The processor-implementedmethod of claim 1 wherein the collected user input is communicated tothe application server.
 5. The processor-implemented method of claim 1wherein: the notification UI form allows a user to specify analternative device at which to receive the notification; and thenotification is a graphical display that pops up over part of agraphical user interface display of the client device.
 6. Theprocessor-implemented method of claim 1 wherein user interface elementsof the notification UI form are transferred to the client device in acommunication that is separate from receipt of the notification; and thenotification is a graphical display that pops up over part of agraphical user interface display of the client device.
 7. Theprocessor-implemented method of claim 1, wherein: the notification UIform includes a comment field to input text; and the notification is agraphical display that pops up over part of a graphical user interfacedisplay of the client device.
 8. The processor-implemented method ofclaim 1 wherein the callback specification further specifies anotification server as a destination for responding to the notification,the method further comprising: communicating the collected user input tothe notification server according to the callback specification.
 9. Acommunications-network-connected client device comprising: a memory; oneor more processor units; a notification server interface stored in thememory and executable by the one or more processor units, thenotification server interface configured to receive a notificationincluding a notification UI form specification and a callbackspecification, the notification being sent to the notification serverinterface in response to a notification request received from anapplication server associated with an application installed on theclient device, the callback specification specifying both an expectedcallback from a user in response to the notification and a uniformresource identifier (URI) or uniform resource locator (URL), thenotification pertaining to the application installed on the clientdevice; a notification UI forms processing module stored in the memoryand executable by the one or more processor units, the notification UIforms processing module configured to present a notification UI form forthe received notification and defined by the notification UI formspecification for display in a user interface of the client devicewithout invoking the installed application, the notification UI formincluding at least one input control; and an input/output module storedin the memory and executable by the one or more processor units, theinput/output module configured to collect user input associated with theinstalled application via the at least one input control of thenotification UI form displayed in the user interface of the clientdevice without invoking the installed application and to communicate thecollected user input to the application server associated with theinstalled application that the notification pertains to according to thecallback specification without invoking the installed application. 10.The communications-network-connected client device of claim 9, wherein:the notification UI form includes a comment field to input text; and thenotification is a graphical display that pops up over part of agraphical user interface display of the client device.
 11. Thecommunications-network-connected client device of claim 9, wherein thecallback specification further specifies the notification server as adestination for responding to the notification, the notification serverinterface being further configured to communicate the collected userinput to the notification server according to the callbackspecification.
 12. One or more tangible computer-readable storage mediastoring computer executable instructions for performing a computerprocess on a client device, the computer process comprising: receiving,at the client device, a notification including a notification UI formspecification and a callback specification, the notification being sentto a client device in response to a notification request received froman application server associated with an application installed on theclient device, and the callback specification specifying both anexpected callback in response to the notification and a uniform resourceidentifier (URI) or uniform resource locator (URL), the notificationpertaining to the application installed on the client device;displaying, by the client device and without invoking the installedapplication, a notification UI form for the received notification anddefined by the notification UI form specification in a user interface ofthe client device, the notification UI form including at least one inputcontrol; collecting user input associated with the installed applicationvia the at least one input control of the notification UI form displayedin the user interface of the client device according to the callbackspecification; and communicating the collected user input to theapplication server associated with the installed application that thenotification pertains to according to the callback specification withoutinvoking the installed application.
 13. The one or more tangiblecomputer-readable storage media of claim 12 wherein the computer processfurther comprises: validating the received notification beforedisplaying the notification UI form in the user interface of the clientcomputing device.
 14. The one or more tangible computer-readable storagemedia of claim 12 wherein the collected user input is communicated tothe application server.
 15. The one or more tangible computer-readablestorage media of claim 12 wherein: the notification UI form allows auser to specify an alternative device at which to receive thenotification; and the notification is a graphical display that pops upover part of a graphical user interface display of the client device.16. The one or more tangible computer-readable storage media of claim 12wherein user interface elements of the notification UI form aretransferred to the client device in a communication that is separatefrom receipt of the notification; and the notification is a graphicaldisplay that pops up over part of a graphical user interface display ofthe client device.
 17. The one or more tangible computer-readablestorage media of claim 12, wherein the computer process furthercomprises: authenticating the received notification before displayingthe notification UI form in the user interface of the client device. 18.The one or more tangible computer-readable storage media of claim 12,wherein: the notification UI form includes a comment field to inputtext; and the notification is a graphical display that pops up over partof a graphical user interface display of the client device.
 19. The oneor more tangible computer-readable storage media of claim 12, whereinthe callback specification further specifies a notification server as adestination for responding to the notification, the computer processfurther comprising: communicating the collected user input to thenotification server according to the callback specification.
 20. The oneor more tangible computer-readable storage media of claim 12, whereinthe notification request received from the application server includes anotification target identification.